Method for performing wake-on-lan management and network system

ABSTRACT

A method for performing wake-up management and an associated apparatus are provided. The method receives device information of a network device by a wake-on-LAN (WOL) agent, wherein the WOL agent and the network device are positioned in a same LAN. The method further receives a request, from a client device, to access the network device. Finally, the method sends a WOL packet, by the WOL agent, to the network device if the device information indicates that the network device is in a non-operating state.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation Application of co-pending U.S. patentapplication Ser. No. 15/458,987, filed Mar. 15, 2017, which claimspriority of Taiwan Patent Application No. 105122842, filed on Jul. 20,2016, the entirety of which is hereby incorporated by reference.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to automation management of referenceinformation for remotely waking up one or more network devices, and moreparticularly, to a method and associated apparatus for performingwake-up management.

2. Description of the Related Art

When performing wake-on-LAN (WOL) operations, a WOL agent in a relatedart local area network (LAN) requires manual settings by a user (e.g.the administrator of the LAN). Some problems may be encountered in therelated art schemes. For example, in order for the WOL agent to havesufficient information for performing WOL operations upon any of aplurality of network devices in the LAN, the user must set referenceinformation for each of the network devices, which wastes a lot of time.The amount of time wasted is increased when the network devices aremany, resulting in an unsatisfying user experience. Hence, there is aneed for a novel method and associated architecture which can performWOL operations without introducing unwanted side effects.

SUMMARY OF THE INVENTION

An objective of the present invention is to provide a method andassociated apparatus for performing wake-up management, in order tosolve the aforementioned problem.

Another objective of the present invention is to provide a method andassociated apparatus for performing wake-up management, in order toraise the overall efficiency of a network system.

At least one embodiment of the present invention provides a method forperforming wake-up management, wherein the method is applied to at leastone portion (e.g. part or all) of a network system, wherein the networksystem comprises a local area network (LAN). The method comprises:utilizing a wake-on-LAN (WOL) agent device to receive device informationof a network device, wherein the WOL agent device and the network deviceare positioned in the LAN, and the network device broadcasts the deviceinformation according to a predetermined communications protocol;utilizing the WOL agent device to refer to the device information of thenetwork device to update a wake-up management list in the WOL agentdevice, wherein the wake-up management list comprises the deviceinformation of the network device; and utilizing the WOL agent device toperform a WOL operation regarding the network device according to thewake-up management list.

In addition to the above method, the present invention also provides anapparatus for performing wake-up management, wherein the apparatus maycomprise at least one portion of a network system, and the networksystem may comprise a LAN. The apparatus comprises a wake-on-LAN (WOL)agent device which is positioned in the LAN. The WOL agent device isarranged to perform wake-up control, wherein the WOL agent devicereceives device information of a network device. The network device ispositioned in the LAN, and the network device refers to a predeterminedcommunications protocol to broadcast the device information of thenetwork device. The WOL agent device refers to the device information ofthe network device to update a wake-up management list in the WOL agentdevice, wherein the wake-up management list comprises the deviceinformation of the network device. The WOL agent device refers to thewake-up management list to perform a WOL operation regarding the networkdevice.

In some embodiments, any of the network devices in the LAN may utilizethe aforementioned predetermined communications protocol (e.g. one ofexisting protocols) to communicate with the WOL agent device bybroadcasting. For example, when a specific network device within thenetwork devices enters a non-operating state, such as a sleep state or apower off state, the WOL agent device may connect (or link) to a keeperdevice and establish a network connection with the keeper device, inorder to inform the keeper device of the non-operating state of thenetwork device via the network connection. In another example, the WOLagent device and the keeper device may establish a network connection inadvance, wherein when a specific network device of the network devicesenters a non-operating state, such as a sleep state or a power offstate, the WOL agent device may inform the keeper device of thenon-operating state of the network device via the network connection.Further, a client device may communicate with the WOL agent device orone of the network devices through the keeper device. In someembodiments, the keeper device may manage a plurality of LANs. Forexample, a plurality of WOL agent devices and a plurality of networkdevices may be positioned in at least one LAN of the LANs, wherein oneof the WOL agent devices may be a backup device of another of the WOLagent devices.

The method and associated apparatus of the present invention mayproperly solve related art problems without introducing unwanted sideeffects. Further, the method and associated apparatus of the presentinvention may raise the overall efficiency of the system. Moreover, themethod and associated apparatus of the present invention are compatiblewith fault-tolerant architectures, and thus the wake-up managementarchitecture based on the method and apparatus of the present inventionmay raise the user experience.

These and other objectives of the present invention will no doubt becomeobvious to those of ordinary skill in the art after reading thefollowing detailed description of the embodiment that is illustrated inthe various figures and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a network system according to anembodiment of the present invention.

FIG. 2 is a diagram illustrating a wake-up management architecture ofthe network system shown in FIG. 1 according to an embodiment of thepresent invention.

FIG. 3 is a diagram illustrating a broadcast operation in the wake-upmanagement architecture shown in FIG. 2.

FIG. 4 is a diagram illustrating a network system according to anotherembodiment of the present invention.

FIG. 5 is a diagram illustrating a broadcast operation in the wake-upmanagement architecture shown in FIG. 4.

FIG. 6 is a diagram illustrating a wake-up management architecture ofthe network system shown in FIG. 1 according to another embodiment ofthe present invention.

FIG. 7 is a diagram illustrating a switching operation in the wake-upmanagement architecture shown in FIG. 6.

FIG. 8 is a broadcast operation in the wake-up management architectureshown in FIG. 6.

FIG. 9 is a diagram illustrating a network system according to anotherembodiment of the present invention.

DETAILED DESCRIPTION

The embodiments of the present invention provide methods and associatedapparatus for performing automatic wake-up management of a networkdevice in at least one local area network (LAN), and automaticallyoperating at least one wake-on-LAN (WOL) agent device. According to amethod and associated apparatus of the present invention, the wake-upmanagement architecture may perform broadcasting via a predeterminedcommunications protocol, such as one of existing communicationsprotocols. Hence, in the WOL agent device, the WOL configurations (e.g.basic LAN information of the network devices), and the states of thenetwork devices may be dynamically set without the need for manualsettings. Further, a keeper device may be positioned in the wake-upmanagement architecture. By utilizing the keeper device, the user mayeasily manage any of a plurality of LANs. In addition, the wake-upmanagement architecture may be applied to the Internet of Things (IoT),sensor networks, etc.

FIG. 1 is a diagram illustrating a network system 100 according to anembodiment of the present invention. The network system 100 may includea client device 110, a keeper device 120, and LN LANs {LAN(1), . . . ,LAN(LN)}, in which the symbol LN may represent a positive integer, and awake-on-LAN (WOL) architecture may be positioned in each of theaforementioned LN LANs {LAN(1), . . . , LAN(LN)}. Examples of the clientdevice 110 may include (but are not limited to): a multifunctionalmobile phone, tablet, wearable device, and personal computer (e.g. alaptop PC or a desktop PC). In this embodiment, the network system 100may include LN WOL agent devices {130-1, . . . , 130-LN} and LN sets ofnetwork devices {{Device(1, 1), Device(1, 2), . . . , Device(1, DN(1))},. . . {Device(LN, 1), Device(LN, 2), . . . , Device(LN, DN(LN))}}, andthe LN WOL agent devices {130-1, . . . , 130-LN} and the LN sets ofnetwork devices {{Device(1, 1), Device(1, 2), . . . , Device(1, DN(1))},. . . {Device(LN, 1), Device(LN, 2), . . . , Device(LN, DN(LN))}} areplaced in the LN LANs {LAN(1), . . . , LAN(LN)}, in which the symbols“DN(1)”, . . . “DN(LN)” represent positive integers. Examples of the WOLagent devices {130-1, . . . , 130-LN} may include (but are not limitedto): routers, network attached storage (NAS) servers, personalcomputers, and electronic devices equipped with WOL functions. Examplesof the network devices {{Device(1, 1), Device(1, 2), . . . , Device(1,DN(1))}, . . . {Device(LN, 1), Device(LN, 2), . . . , Device(LN,DN(LN))}} may include (but are not limited to): personal computers, andNAS servers. As shown in FIG. 1, the WOL agent devices {130-1, . . . ,130-LN} may generate and store the wake-up management lists {132-1, . .. , 132-LN}, respectively. Further, the WOL agent devices {130-1, . . ., 130-LN} may dynamically update the wake-up management lists {132-1, .. . , 132-LN}, and may refer to the wake-up management lists {132-1, . .. 132-LN} to respectively perform wake-up management upon the LN sets ofnetwork devices {{Device(1, 1), Device(1, 2), . . . , Device(1, DN(1))},. . . {Device(LN, 1), Device(LN, 2), . . . , Device(LN, DN(LN))}}.

In this embodiment, the apparatus for performing wake-up management mayinclude at least one portion (e.g. part or all) of the network system100, such as a wake-up management system 100S in the network system 100,or any portion of the wake-up management system 100S (e.g. the keeperdevice 120 or any of the WOL agent devices {130-1, . . . , 130-LN}). Asshown in FIG. 1, the wake-up management system 100S may include thekeeper device 120 and the WOL agent devices {130-1, . . . , 130-LN}, andmay comprise LN communications channels between the keeper device 120and the WOL agent devices {130-1, . . . , 130-LN}. Further, theaforementioned WOL architecture may be extended external to the LAN viathe LN communications channels, and more particularly, external to thekeeper device 120. The client device 110 may access a target networkdevice through the keeper device 120, such as any network device withinthe aforementioned LN sets of network devices {{Device(1, 1), Device(1,2), . . . , Device(1, DN(1))}, . . . {Device(LN, 1), Device(LN, 2), . .. , Device(LN, DN(LN))}}, in which when the target network device is inthe non-operating state, the keeper device 120 may trigger the WOLarchitecture to perform a WOL operation.

Regarding the WOL operations of the aforementioned WOL architecture,when the target network device has entered the non-operating state (e.g.a sleep state or a power off state), the WOL agent device in the sameLAN may send a predetermined package, such as a WOL package. Moreparticularly, the WOL agent device may broadcast the predeterminedpackage, to make the target network device enter the operating statefrom the non-operating state, in which the predetermined package maycarry the media access control (MAC) address (e.g. the physical address)of the target network device. Under the situation where the targetnetwork device is in the sleep state, when the target network devicereceives the predetermined package, the target network can be woken up.In another example, under the situation where the target network deviceis in the power off state, when the target network device receives thepredetermined package, the target network device may automatically poweron in order to enter the power on state from the power off state.

The aforementioned WOL operation is based on the WOL configurations ofthe WOL agent device. In this embodiment, each of the WOL agent devices{130-1, . . . , 130-LN} may automatically perform WOL configurationswithout the need for manual settings by the user (e.g. the administratorof the wake-up management system 100S). For example, one or more networkdevices in the network system 100 may be dynamically removed, and theWOL agent device in the LAN to which the one or more network devicesbelong may automatically perform WOL configurations, and report thelatest state to the keeper device 120. In another example, one or morenetwork devices may be dynamically added to the network system 100, andthe WOL agent device in the LAN to which the one or more network devicesbelong may automatically perform WOL configurations, and report thelatest state to the keeper device 120. In another example, one or moreWOL agent devices may be dynamically added to the network system 100,and a WOL agent device that operates in the LAN to which the newly addedone or more WOL agent devices belong may automatically perform WOLconfigurations, and report the latest state to the keeper device 120.Hence, the wake-up management architecture based on the method andassociated apparatus of the present invention may solve the related artproblems.

Regarding the automatic WOL configurations of any WOL agent device130-ln within the WOL agent devices {130-1, . . . , 130-LN}, the WOLagent device 130-ln may receive the device information of any networkdevice within the ln-th set of network devices {Device(ln, 1),Device(ln, 2), . . . , Device(ln, DN(ln))}, in which the symbol “ln” isa positive integer between [1, LN]. More particularly, the WOL agentdevice 130-ln may utilize the predetermined communications protocol toreceive the device information of the network device, in which thenetwork device may refer to the predetermined communications protocol tobroadcast the device information of the network device. For example,when the state of the network device changes, the network device mayrefer to the predetermined communications protocol to broadcast thedevice information of the network device, allowing the WOL agent device130-ln to automatically obtain and record the device information of thenetwork device. In this embodiment, the WOL agent device 130-ln mayrefer to the device information of the network device to update thewake-up management list 132-ln, in which the wake-up management list132-ln may include the device information of the network device. Hence,the WOL agent device 130-ln may refer to the wake-up management list132-ln to perform WOL operations regarding the network device. Forexample, the network device may refer to the predeterminedcommunications protocol to perform at least one broadcast operation,allowing the WOL agent device 130-ln to determine state transitions ofthe network device. In response to the broadcast operation, the WOLagent device 130-ln may determine the state transitions of the networkdevice to automatically perform WOL configurations regarding the networkdevice.

The aforementioned automatic WOL configuration is not limited to beapplied to a single network device. Based on the architecture of thepresent invention, the automatic WOL configuration is applicable tomultiple network devices. For example, the WOL agent device 130-ln mayreceive device information of another network device within the ln-thset of network devices {Device(ln, 1), Device(ln, 2), Device(ln,DN(ln))}, and more particularly, may utilize the predeterminedcommunications protocol to receive the device information of the othernetwork device, in which the other network device may refer to thepredetermined communications protocol for broadcasting the deviceinformation of the other network device. For example, when the state ofthe other network device changes, the other network device may refer tothe predetermined communications protocol to broadcast the deviceinformation of the other network device, allowing the WOL agent device130-ln to automatically obtain and record the device information of theother network device. In this embodiment, the WOL agent device 130-lnmay refer to the device information of the other network device toupdate the wake-up management list 132-ln, in which the wake-upmanagement list 132-ln may include the device information of the othernetwork device. Hence, the WOL agent device 130-ln may refer to thewake-up management list 132-ln to perform a WOL operation upon the othernetwork device.

FIG. 2 is a diagram illustrating a wake-up management architecture ofthe network system shown in FIG. 1 according to an embodiment of thepresent invention. For better understanding, the network devices{Device(1), Device(2), Device(3), Device(4)} are illustrated as anexample of the ln-th set of network devices {Device(ln, 1), Device(ln,2), . . . , Device(ln, DN(ln))}, the WOL agent device 230 is an exampleof the WOL agent device 130-ln, and the wake-up management list 232 isan example of the wake-up management list 132-ln. In this situation,DN(ln)=4; however, this is merely for illustrative purposes, and is nota limitation of the present invention. In some embodiments, the numberof network devices in the ln-th set of network devices {Device(ln, 1),Device(ln, 2), . . . , Device(ln, DN(ln))} can be changed.

In this embodiment, the WOL agent device 230 may receive the deviceinformation of each of the network devices {Device(1), Device(2),Device(3), Device(4)}, and more particularly, may utilize thepredetermined communications protocol to receive device information ofthe network devices {Device(1), Device(2), Device(3), Device(4)}, inwhich the network devices {Device(1), Device(2), Device(3), Device(4)}may refer to the predetermined communications protocol to broadcast thedevice information of the network device. For example, when the state ofa specific network device within the network devices {Device(1),Device(2), Device(3), Device(4)} changes, the network device may referto the predetermined communications protocol to broadcast the deviceinformation of the network device, to allow the WOL agent device 230 toautomatically obtain and record the device information of the networkdevice, in order to update the wake-up management list 232, in which thewake-up management list 132-ln may include the device information andthe latest state of the network device.

FIG. 3 is a diagram illustrating a broadcast operation in the wake-upmanagement architecture shown in FIG. 2. For better understanding, thenetwork device Device(4) may be an example of the aforementionedspecific network device; however, this is merely for illustrativepurposes, and not a limitation of the present invention. Note that anyother network device within the network devices {Device(1), Device(2),Device(3), Device(4)} may an example of the aforementioned specificnetwork device.

In this embodiment, when the network device Device(4) refers to thepredetermined communications protocol to broadcast the deviceinformation of the network device Device(4), the device informationbroadcasted by the network device Device(4) may comprise at least one ofthe MAC address of the network device Device(4), an Internet protocol(IP) address of the network device Device(4), and an unique identifier(UID) of the network device Device(4). Hence, the WOL agent device 230may record at least one of the MAC address of the network deviceDevice(4), the IP address of the network device Device(4), and the UIDof the network device Device(4) in the wake-up management list 232, andmay record the latest state (the sleep/awake state, such as power on/offstate) of the network device Device(4) in the wake-up management list232, in order to update the wake-up management list 232.

When the network device Device(4) is added to the LAN LAN(ln) for thefirst time, the network device Device(4) is in the operating state.Hence, the WOL agent device 230 may record at least one of the MACaddress of the network device Device(4), the IP address of the networkdevice Device(4), and the unique identifier (UID) of the network deviceDevice(4) in the wake-up management list 232, and may record theoperating state of the network device Device(4) in the wake-upmanagement list 232. After that, when the WOL agent device 230 receivesthe device information broadcasted by the network device Device(4), theWOL agent device 230 may determine that the network device Device(4) isswitching between the operating state and the non-operating state. Sincethe network device Device(4) may toggle between the operating state andthe non-operating state, when the information broadcasted by the networkdevice Device(4) is received, the WOL agent device 230 may refer to aprevious state of the network device Device(4) to determine that thelatest state of the network device Device(4) is in contrast with theprevious state. For example, since the previous state is the contrarystate of the latest state, if the previous state of the network deviceDevice(4) is the operating state, the latest state of the network deviceDevice(4) will be the non-operating state, and vice versa.

Before the network device Device(4) enters the non-operating state, thenetwork device Device(4) may refer to the predetermined communicationsprotocol to broadcast the device information of the network deviceDevice(4) in order to inform the WOL agent device 230 of thenon-operating state of the network device Device(4). Further, afterbeing informed of the non-operating state of the network deviceDevice(4), the WOL agent device 230 may record the non-operating stateof the network device Device(4) in the wake-up management list 232. Inanother example, when the network device Device(4) enters the operatingstate from the non-operating state, the network device Device(4) mayrefer to the predetermined communications protocol to broadcast thedevice information of the network device Device(4) in order to informthe WOL agent device 230 of the operating state of the network deviceDevice(4). Further, after learning the operating state of the networkdevice Device(4), the WOL agent device 230 may record the operatingstate of the network device Device(4) in the wake-up management list232.

In some embodiments, it is not a necessary step that the WOL agentdevice 230 refers to the previous state of the network device Device(4)to determine the latest state of the network device Device(4). Forexample, when the network device Device(4) refers to the predeterminedcommunications protocol to broadcast the device information of thenetwork device Device(4), the device information broadcasted by thenetwork device Device(4) may comprise at least one of the MAC address ofthe network device Device(4), the IP address of the network deviceDevice(4), and the unique identifier (UID) of the network deviceDevice(4), and may further comprise the latest state of the networkdevice Device(4) (the sleep/awake state or power on/off state). Hence,the WOL agent device 230 may record at least one of the MAC address ofthe network device Device(4), the IP address of the network deviceDevice(4), and the unique identifier (UID) of the network deviceDevice(4) in the wake-up management list 232, and may record theoperating state of the network device Device(4) in the wake-upmanagement list 232.

Note that no matter whether the device information broadcasted by thenetwork device Device(4) comprises the latest state of the networkdevice Device(4) or not, since the wake-up management list 232 storesthe latest state of the network device Device(4) (e.g. the sleep/awakestate, such as power off/on state), the WOL agent device 230 may referto the wake-up management list 232 to selectively perform a WOLoperation regarding the network device Device(4) (e.g. theaforementioned WOL operation). In some embodiments, under the situationwhere the wake-up management list 232 indicates that the network deviceDevice(4) is in the non-operating state, the WOL agent device 230 mayperform WOL operation regarding the network device Device(4) (e.g. theclient device 110 accesses the network device Device(4) through thekeeper device 120) when there is a need; otherwise, the WOL agent device230 does not perform the WOL operation regarding the network deviceDevice(4).

In some embodiments, the way of implementing the wake-up control may bemodified. For example, under the situation where the wake-up managementlist 232 indicates that the network device Device(4) is in the operatingstate, when triggering is performed (e.g. the client device 110 accessesthe network device Device(4) through the keeper device 120), the WOLagent device 230 may perform a WOL operation regarding the networkdevice Device(4), such as the aforementioned WOL operation, even if thenetwork device Device(4) is already in the operating state. In theseembodiments, although the network device Device(4) is already in theoperating state, the WOL operation will not interfere with theoperations of the network device Device(4).

In some embodiments, assuming that the network device Device(4) shown inFIG. 3 is the target network device, and the target network device is inthe ln-th LAN LAN(ln), during the aforementioned automation WOLconfiguration, the WOL agent device 130-ln may utilize the predeterminedcommunications protocol to receive the device information of the networkdevice Device(4), and may send the device information of the networkdevice Device(4) to the keeper device 120. The device information sentfrom the WOL agent device 130-ln to the keeper device 120 may include atleast one state of the network device Device(4), such as the lateststate thereof. Further, the client device 110 may send a request to thekeeper device 120, in order to access the target network device throughthe keeper device 120. When the keeper device 120 receives the requestfrom the client device 110, the keeper device 120 may refer to the stateof the network device Device(4) to decide whether to assign a WOL taskto the WOL agent device 130-ln, wherein the WOL task comprises waking-upthe network device Device(4). For example, when the latest state of thenetwork device Device(4) is non-operating, the keeper device 120 mayassign the WOL task to the WOL agent device 130-ln, in order to wake-upthe network device Device(4); otherwise, the keeper device 120 does notassign the WOL task to the WOL agent device 130-ln.

Analogous controls may be applied to any other LAN in the network system100, and may be applied to another WOL agent device (which is configuredin the other LAN), in order to perform wake-up management of anothertarget network device (e.g. any network device in the other LAN). Duringthe aforementioned automation WOL configuration, the other WOL agentdevice may utilize the predetermined communications protocol to receivethe device information of the other target network device, and may senddevice information of the other target network device to the keeperdevice 120, wherein the device information (e.g. the device informationof the other target network device) sent from the other WOL agent deviceto the keeper device 120 may comprise at least one state of the othertarget network device, such as the latest state thereof. The clientdevice 110 may send another request to the keeper device 120 in order toaccess the other target network device through the keeper device 120.When the keeper device 120 receives the other request of the clientdevice 110, the keeper device 120 may refer to the state of the othertarget network device to decide whether to assign another WOL task tothe other WOL agent device, wherein the other WOL task compriseswaking-up the other target network device. For example, when the lateststate of the other target network device is non-operating, the keeperdevice 120 may assign the other WOL task to the other WOL agent device,in order to wake-up the other target network device; otherwise, thekeeper device 120 does not assign the other WOL task to the other WOLagent device.

FIG. 4 is a diagram illustrating a network system according to anotherembodiment of the present invention. Compared with the WOL agent device230 shown in FIG. 2, the WOL agent device 330 in this embodiment is anetwork device selected from various network devices in the LAN LAN(ln),such as the network device Device(1). The wake-up management list 232 inthis embodiment is replaced by the wake-up management list 332. Forbetter understanding, in the embodiment of FIG. 4, the network deviceDevice(1) is selected as the WOL agent device 330; however, this ismerely for illustrative purposes, and not a limitation of the presentinvention. Any network device within the network devices {Device(1),Device(2), Device(3), Device(4)} other than the network device Device(1)may also be selected as the network device.

FIG. 5 is a diagram illustrating a broadcast operation in the wake-upmanagement architecture shown in FIG. 4. In this embodiment, the WOLagent device 330 may perform the aforementioned operations of the WOLagent device 230. Some features in this embodiment similar to those inthe above embodiments/modifications are omitted here for brevity.

FIG. 6 is a diagram illustrating a wake-up management architecture ofthe network system shown in FIG. 1 according to another embodiment ofthe present invention. In this embodiment, a specific network devicewithin the network devices {Device(1), Device(2), Device(3), Device(4)}may be selected as an initial WOL agent device according to apredetermined rule, such as a default WOL agent device. Further, exceptfor the initial WOL agent device, any network device within the networkdevices {Device(1), Device(2), Device(3), Device(4)} other than theselected initial network device may be selected as a backup device ofthe initial network device. If the WOL agent device 430A and the wake-upmanagement list 432A thereof are equivalent to the WOL agent device 330and the wake-up management list 332 thereof shown in FIG. 4, it meansthat the network device Device(1) plays the role of the WOL agent device430A.

In this embodiment, before the WOL agent device 430A enters thenon-operating state, the WOL agent device 430A may refer to thepredetermined communications protocol to broadcast device information ofthe WOL agent device 430A in order to inform other network devices inthe ln-th LAN LAN(ln) of the non-operating state of the WOL agent device430A. Further, the non-operating state of the WOL agent device 430A willtrigger the backup architecture of the LAN LAN(ln). When thenon-operating state of the WOL agent device 430A is obtained, the WOLagent device 430A may be replaced by at least one of the other networkdevices.

When the WOL agent device 430A is replaced by the network deviceDevice(1), any other network device within the network devices{Device(1), Device(2), Device(3), Device(4)}, such as the networkdevices Device(2), Device(3) or Device(4), may be selected as the backupdevice of the initial WOL agent device according to the predeterminedrule. For example, the predetermined rule may represent a predeterminedorder of the network devices {Device(1), Device(2), Device(3),Device(4)}, such as the order of the indexes 1-4 corresponding to thenetwork devices Device(1), Device(2), Device(3) and Device(4),respectively. This is merely for illustrative purposes, and not alimitation of the present invention. In some embodiments, thepredetermined rule may represent one predetermined order of the networkdevice in a predetermined subset of the network devices {Device(1),Device(2), Device(3), Device(4)} (e.g. the subset comprising the networkdevices Device(1) and Device(2)).

FIG. 7 is a diagram illustrating a switching operation in the wake-upmanagement architecture shown in FIG. 6. For example, the network deviceDevice(1), which previously played the role of the WOL agent device430A, stops playing the role of the WOL agent device 430B. Hence, thelatest WOL agent device in the LAN LAN(ln) becomes the WOL agent device430B.

Compared with the WOL agent device 230 shown in FIG. 2, the WOL agentdevice 430B in this embodiment is a network device selected from variousnetwork devices in the LAN LAN(ln), such as the network deviceDevice(2). In response to the change in architecture, the aforementionedwake-up management list 232 is replaced by the wake-up management list432B in this embodiment. For better understanding, the network deviceDevice(2) may be an example of the selected network device. Note thatany network device within the network devices {Device(1), Device(2),Device(3), Device(4)} except for the network device that is going toenter the non-operating state (e.g. the network device Device(1)) may bean example of the selected network device (i.e. the selected WOL agentdevice).

According to some embodiments, the WOL agent device 430A may send thewake-up management list 432A to the WOL agent device 430B, to allow theWOL agent device 430B to use the wake-up management list 432A. Forexample, the WOL agent device 430B may use the wake-up management list432A as an initial version of the wake-up management list 432B. Somefeatures in this embodiment similar to those in the aboveembodiments/modifications are omitted here for brevity.

FIG. 8 is a broadcast operation in the wake-up management architectureshown in FIG. 6. In this embodiment, the WOL agent device 430B mayperform the aforementioned operations of the WOL agent device 230. Somefeatures in this embodiment similar to those in the aboveembodiments/modifications are omitted here for brevity.

FIG. 9 is a diagram illustrating a network system 500 according toanother embodiment of the present invention. For better understanding,the LANs {LAN(1), LAN(2), LAN(3)} in FIG. 9 may be an example of theaforementioned LN LANs {LAN(1), . . . , LAN(LN), and the three sets ofnetwork devices {{Device(1, 1), Device(1, 2), . . . , Device(1, DN(1))},. . . {Device(2, 1), Device(2, 2), . . . , Device(2, DN(2))}, . . .{Device(3, 1), Device(3, 2), . . . , Device(3, DN(3))}} shown in FIG. 9may be an example of the aforementioned LN sets of network devices{{Device(1, 1), Device(1, 2), . . . , Device(1, DN(1))}, . . .{Device(LN, 1), Device(LN, 2), . . . , Device(LN, DN(LN))}}. The WOLagent device of some LANs may be implemented as a fault tolerancearchitecture, wherein LN=3. According to some embodiments, the number ofthe aforementioned LN LANs {LAN(1), . . . , LAN(LN) (or the number ofthe aforementioned LN sets of network devices) may be modified.

In this embodiment, each of the WOL agent devices 130-1, 130-2A, 130-2B,130-3A and 130-3B may create a communications channel leading to thekeeper device 120, and the WOL agent devices 130-1, 130-2A, 130-2B,130-3A and 130-3B may manage the wake-up management lists 132-1, 132-2A,132-2B, 132-3A and 132-3B, respectively. Further, the WOL agent devices130-2A and 130-2B may form a single WOL agent fault tolerancearchitecture. For example, one WOL agent device of the WOL agent devices130-2A and 130-2B may operate in a default manner, and the other WOLagent device of the WOL agent devices 130-2A and 130-2B may be thebackup device of the WOL agent device. In addition, the WOL agentdevices 130-3A and 130-3B may form a multiple WOL agent fault tolerancearchitecture. For example, the WOL agent devices 130-3A and 130-3B maysimultaneously operate, and may be each other's backup device. Accordingto some embodiments, the aforementioned fault tolerance architecture(e.g. a single WOL agent fault tolerance architecture or the multipleWOL agent fault tolerance architecture) may be modified.

According to some embodiments, before any WOL agent device of thenetwork system 500 enters the non-operating state (e.g. the sleep orpower off state), the WOL agent device may inform other network devicesor WOL agent devices of its current state by broadcasting. Hence, thefault tolerance architecture of the WOL agent device in the LAN mayrefer to its fault tolerance method to perform fault toleranceprocesses, in order to maintain the wake-up management operation.

According to some embodiments, the keeper device 120 may automaticallymanage the WOL information in the network system 500, to allow the userto easily use any LAN in the network system 500, without the need formanual settings. When the network device in any LAN of the networksystem 500 changes its state, one or more WOL agent devices in the LANmay communicate with the keeper device 120 via correspondingcommunications channels. Further, the keeper device 120 may recordvarious states of each LAN in the network system 500, such as the stateindicating which devices are managed by which WOL agent device. Thekeeper device 120 may manage multiple LANs such as those shown in FIG.9, wherein the number of WOL agent devices in each LAN is not limited.Referring to the scheme shown in FIG. 9, the keeper device 120 mayrecord respective management information of the three LANs {LAN(1),LAN(2), LAN(3)}, and the user may operate or access devices in any LANand WOL agent device through the keeper device 120.

The method and associated apparatus of the present invention may solveproblems existing in the related art without introducing unwanted sideeffects. Further, the method and associated apparatus of the presentinvention may raise the overall efficiency. For example, the networkdevices and the WOL agent devices do not need to be preset, nor do theyneed to learn of each other's existence in advance. In another example,any of the network devices and the WOL agent devices may be dynamicallyadded into a LAN. In another example, the client device 110 may easilymanage or access network devices of any of the LANs through the keeperdevice 120. In addition, the method and associated apparatus of thepresent invention is compatible with fault tolerance architecture. Whena specific WOL agent device stops providing services, or enters thepower off state, the fault tolerance architecture positioned in the sameLAN may automatically solve this problem, wherein the fault tolerancearchitecture may be implemented as a failover architecture havingmultiple WOL agent devices, or a failback architecture having a singleWOL agent device. For example, when adopting the failover architecture,with the aid of the automatic managing architecture of the keeper device120, the client device 110 does not need to communicate with each WOLagent device. In another example, when the failback architecture isadopted, with the aid of the automatic managing architecture of thekeeper device 120, problems such as a missing WOL agent device can beprevented. Hence, the wake-up management architecture based on themethod and associated apparatus of the present invention can improve theuse experience.

Those skilled in the art will readily observe that numerousmodifications and alterations of the device and method may be made whileretaining the teachings of the invention. Accordingly, the abovedisclosure should be construed as limited only by the metes and boundsof the appended claims.

What is claimed is:
 1. A method for performing wake-on-LAN (WOL)management, the method comprising: receiving device information of anetwork device by a wake-on-LAN (WOL) agent, wherein the WOL agent andthe network device are positioned in a same LAN; and receiving arequest, from a client device, to access the network device; and sendinga WOL packet, by the WOL agent, to the network device if the deviceinformation indicates that the network device is in a non-operatingstate.
 2. The method of claim 1, wherein the sending of the WOL packetfurther comprising broadcasting the WOL packet within the LAN.
 3. Themethod of claim 1, further comprising determining operating ornon-operating state of the network device by the WOL agent beforesending the WOL packet.
 4. The method of claim 1, further comprising:broadcasting, by the WOL agent, device information of the WOL agentwithin the LAN before the WOL agent enters a non-operating state.
 5. Themethod of claim 1, further comprising: updating a wake-up managementlist by the WOL agent, wherein the wake-up management list comprises thedevice information of the network device.
 6. The method of claim 1,further comprising: sending, by the WOL agent, the device information ofthe network device to a keeper device.
 7. A method for performingwake-on-LAN(WOL) management, the method comprising: sending, by anetwork device, device information to a WOL agent before entering anon-operating state, wherein the WOL agent and the network device arepositioned in a same LAN; and sending, by the network device, the deviceinformation to the WOL agent after entering the operating state; andwherein the device information comprises an Internet protocol (IP)address of the network device and indicates an operation or anon-operation state of the network device.
 8. The method of claim 7,wherein the sending of the device information by the network device isto broadcast the device information in the same LAN.
 9. The method ofclaim 7, further comprising: receiving a WOL packet from the WOL agentin the same LAN when in a non-operating state.
 10. A network system,comprising: a wake-on-LAN (WOL) agent device positioned in a local areanetwork (LAN); and at least one network device positioned in the sameLAN, the network device sending device information to the WOL agentdevice before entering a non-operating state; wherein the WOL agentdevice stores information of a non-operating or an operating state ofthe network device, and when the WOL agent device receives a requestfrom a client device to access the network device, the WOL agent devicesends a WOL packet to the network device if the network device is in anon-operating state.
 11. The network system of claim 10, wherein thenetwork device sends the device information to the WOL agent deviceafter enters an operating state from the non-operating state.
 12. Thenetwork system of claim 10, wherein the WOL agent device sends thedevice information of the network device to a keeper device external tothe LAN, and when the keeper device receives a request from a clientdevice to access the network device, the keeper device assign a WOL taskto the WOL agent device if the device information indicates that thenetwork device is in a non-operating state.
 13. The network system ofclaim 10, wherein the WOL agent device broadcasts device information ofthe WOL agent device in order to inform at least one other networkdevice in the LAN of the non-operating state of the WOL agent device,and another of the network devices is selected as another WOL agentdevice in the LAN after receiving the device information of the WOLagent device.